Use "validateLogs" for preset-env's debug fixtures #10401
Merged
+1,354
−555
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes preset-env's
debug-fixtures
use the new functionality introduced in #10326This has two main advantages:
time yarn jest preset-env
before this PR:time yarn jest preset-env
after this PR:time yarn jest
before this PR:time yarn jest
after this PR:NOTES:
debug-fixtures
contained two input files. I split them in two different fixturesSuccessfully compiled 1 file with Babel.
disappeared fromstdout
, because it wasn't printed bypreset-env
but by@babel/cli
options.json
orstdout.txt
files are reported as "new" or "deleted" by git. It's just because of the fixtures I duplicated, or because git doesn't properly track renames of small files with many updates.